Initialization of switching networks for use with a scalable coherent interface

ABSTRACT

The Scalable Coherent Interface (SCI) standard of the Institute of Electrical and Electronics Engineers is intended for fast, high throughput, point-to-point, unidirectional links. It is to serve high-performance multiprocessor systems. A number of key elements are defined as part of the protocol for SCI. These include: (a) command.old which is a bit in transmitted packets for detecting stale packets to discard; (b) idle.cc which is an idle bit to be inserted between packets for detecting lost packets which toggles when the idle bit has circulated around the ringlet; and (c) idle.ac which is an idle bit which toggles when all operational nodes have had an opportunity to transmit. In addition, SCI contemplates the implementation of a number of different types of resets, including power reset, upon read or apparent loss of power for more than a second and linc reset for clearing circuits but not changing error count registers in the system. An implementation of SCI for a switching network which does not contain full agent switches (i.e., switches that have queues), as contemplated by SCI is disclosed which extends the utilization of the above-noted key elements. This implementation provides for a substantial reduction in the complexity, size, power and costs of the network. The network may be expandable in that it can service more than the current number of required operational rings which have at least one scrubber node and may have one or more other functional nodes therein, while handling misrouted packets by providing recirculation conductive connections to all input and output ports of the network that are not connected to such operational rings.

BACKGROUND OF THE INVENTION Field of the Invention

The invention relates to the transmission of data packets onunidirectional point-to-point transmission links, and more particularlyto the integration of such point-to-point transmission links withswitched networks.

Background Discussion

The Scalable Coherent Interface (SCI) provides services similar to thosecommonly offered in a computer bus architecture. In a multiprocessorenvironment, however, the scalability of a traditional bus is limited byphysics; specifically, problems associated with tapped transmissionlines, reflections and capacitive loading. To overcome these problemsSCI uses a collection of fast point-to-point unidirectional linksinstead of a physical bus.

A packet transfer protocol is used by SCI to implement varioustransactions on the high speed links. This arrangement scales very wellfrom a small number of nodes to a large number of nodes although thelatency, or the time required to send information from one node toanother increases linearly with the number of nodes if they areconnected in a ring. There are several alternatives to the ring that canreduce latency. The Layered network is one alternative that minimizeslatency and also contributes other advantages such as support for faulttolerance.

This document specifies a Layered network switch that is the centralcomponent required for constructing Layered networks. It is a 3×3 switchwith 3 SCI input ports and 3 SCI output ports. Layered networks usingthe Layered network switch are compatible with SCI packet formats andprotocols.

Terms and Conventions.

For reference consult the following documents: SCIstandard/specification: IEEE Std 1596-1992 IEEE Standard for ScalableCoherent Interface (SCI).

Joint Test Action Group (JTAG) standard/specification: IEEE Std1149.1-1990 (Includes IEEE Std 1149.1a-1993) IEEE Standard Test AccessPort and Boundary Scan Architecture.

Layered Network, U.S. Pat. No. 4,833,468, issued 23 May 1989, Brian R.Larson, et al.

Bit and Byte Ordering.

The addressable unit in SCI is the 8-bit byte. SCI packets areconstructed from 2-byte (doublet) symbols. Bit zero is always the mostsignificant bit of a symbol, byte zero is always the most significantbyte of a symbol, and the most significant doublet of the address alwayscomes first. This is big-endian packet notation.

Numerical Values.

Decimal, hexadecimal, and binary numbers are used within thisspecification. Decimal numbers are represented in their standard 0, 1, 2. . . format. Hexadecimal numbers are represented by a string of one ormore hexadecimal (0-9, A-F) digits followed by the subscript 16. Binarynumbers are represented by a string of one or more binary (0, 1) digitsfollowed by the subscript 2.

Definitions.

This glossary is intended to be a convenient collection of terms usedhere, rather than an exhaustive dictionary. Definitions from the IEEE1596-1992 standard are labeled "in SCI."

Command.

In SCI, the second symbol of every send and echo packet. Fields in thecommand symbol used here are command.mprand command.old.

Command.mpr.

In SCI, carries the maximum ringlet priority. The switch uses this fieldto mark packets according to their original relationship to idle.cc, aspart of the protocol for extending the idle. cc ringlet protocol to theentire system.

Command.old.

In SCI, indicates whether the packet has been through the scrubber. Inthis system, because the scrubber is the first element in the ringletafter leaving the network, command. old also indicates whether thepacket has previously been through the network.

Echo Packet.

In SCI, echo packets are sent by nodes that receive send packets. Theyconfirm to the sender that the send packet was received. They are routedthrough the network in the same manner as send packets.

Idle Symbol.

In SCI, an idle is a symbol that is transmitted whenever there is nopacket being transmitted.

Misrouted Packet.

A misrouted packet is one that leaves the network on the wrong ringlet,that is, a ringlet other than the one containing the packet'sdestination node. It is possible for a packet to be misrouted more thanonce, since it does re-enter the network after not finding itsdestination in the ringlet. Note that a packet is only misrouted whileit is not in the network, since the success of its routing is only knownthen.

Network.

A network is a Layered network consisting of interconnected switches.The switches are arranged in stages, with the first stage acceptingsymbols directly from ringlets and the last stage sending symbols toringlets.

One Misroute.

A one misroute (1-misroute) is a misrouted one packet.

One Packet.

A one packet is a packet that is first transmitted when the last idlereceived on that input port had an idle.cc value of 1. See alsocommand.mpr.

Packet.

In SCI, a packet is a sequence of symbols identified by an initialsymbol with the flag bit set. There are several packet formats; the twoof primary interest here are send and echo packets.

Ringlet.

In SCI, a ringlet is the closed path formed by the connection thatprovides feedback from the output link of a node to its input link.

In this document, a ringlet includes one pair of connections to anetwork, with the scrubber positioned so that it is the first to seesymbols as they come from the network.

Ringlets-per-row.

The Layered Network consists of rows of switch chips. Each row canconnect to either 1 or 2 ringlets. The ringlets are connected to switchports 1 and 2.

Scrubber.

In SCI, an element in the ring that performs several maintenanceoperations on packets--it complements idle.cc and idle.ac, ifcommand.old is clear it sets it, and if set it changes the packet intoan echo packet that indicates an error. There must be exactly onescrubber in a ring. In the Layered network, the scrubber must be thefirst element to process packets after they have left the network.Sometimes, the scrubber is incorporated into the same device as anothernode. In order that the scrubber be the first node after the Layerednetwork, the device must implement the scrubber as logically before theother node.

SCI Node Interface Chip.

The logic that interfaces a node to an SCI ringlet, one example of whichis the VSC7201-SCI DataPump, Vitesse Semiconductor Corporation.

Send Packet.

In SCI, a send packet is a packet that originated at a node as a resultof node activity.

Stale Packet.

In SCI, a stale packet is one that returns to the scrubber without beingaccepted by any node. In this paper a stale packet is a packet thatreturns to the network from its correctly-routed ringlet. It isaddressed to a nonexistent node.

Symbol.

In SCI, a symbol is the information transmitted in one clock period. Itincludes 16 data bits, a flag and a strobe.

System.

A system is a Layered network and a set of ringlets connected to it

Switch.

A switch refers to the switch-point used to construct the Layerednetwork.

Target Address.

In SCI, the target address is the node ID of the packet's destination.It is the first symbol of every packet and is referred to as targeted.

Zero Misroute.

A zero misroute (0-misroute) is a misrouted zero packet.

Zero Packet.

A zero packet is a packet that is first transmitted when the last idlereceived on that input port had an idle.cc value of 0. See alsocommand.mpr.

SCI Overview.

The objective of the SCI standard is to provide a high performanceinterconnect system between processors and memory for tightly coupled,cache coherent data communication. SCI utilizes point-to-point links andpasses data packets to avoid the problems of bus design such as sharedresource bandwidth bottlenecks and design of multi-drop, high speedbackplane transmission lines.

The simplest interconnection of multiple nodes using only point-to-pointlinks is a ring, which sends information in one direction only. The SCIstandard expects nodes to be connected in a ring, or in multipleinterconnected rings, and some of its protocols depend on the behaviorof a ring interconnection.

One method provided in the standard to interconnect rings is withagents, which appear to other nodes on each of two (or more) rings asstandard nodes and can transfer information between the rings. Behaviorof the nodes internally is not covered by the standard.

Another method provided in the standard to interconnect rings is with aninterconnection network, of topology not defined by the standard,provided that the interfaces between the nodes and the network satisfySCI protocols. The Layered network switch is designed for this method.

Layered Network Overview.

The Layered network switch is designed to support the functionalityneeded in a modified Layered network. The network is modified such thata 2-plane network that normally requires a 4-by-4 switch is implementedwith a 3-by-3 switch. The modification saves significant switch chiparea and printed-circuit card area. To provide some background for thisrole, this section describes the Layered network.

The modified Layered network, shown in FIG. 1, consists of connectedLayered network switches and, from a protocol viewpoint, appears to anSCI ring as a wire interconnect--it is neither an SCI agent nor node. InFIG. 1 the cross-hatched, rectangular boxes represent switches of theswitching network. The blank circles are the nodes that form theringlets while the circle with the S in it is the scrubber node. FIG. 1illustrates an embodiment that is disclosed for the purposes ofdescribing the invention, and may not be a practical embodiment for manyapplications since the operational ringlets generally would contain atleast 1 or 2 more operational nodes, even if the scrubber node couldalso provide operational functions. When the switches all route packetsstraight, the effect is of a set of essentially unrelated ringlets. Whenpackets are routed diagonally, they go to different destinationringlets; valid source and destination node ID's are the set of allnodes on all ringlets. The effect of the switch, indeed its purpose, isto implement connection of a large quantity of nodes without paying thedelay penalty of a single large ring.

Switch Position.

For reference purposes the Layered network switches are arranged in amatrix of N rows and n+1 columns (n is log₂ N). The left column, whichreceives SCI packets from rings, is called the first stage or stage 0.The right column, which sends SCI packets to rings, is called the laststage or stage n. The switch rows are numbered from 0 (top) to N-1(bottom). They are associated with SCI rings; each row can connect toeither one or two rings.

Layered network switches are connected in a multi-layer banyan manner.Within the network, each output Port 0 is connected to the input port 0of the next adjacent switch in the same row (straight across). Eachoutput Port 1 is connected to the input port 1 of the layer 1 diagonalswitch in the next stage. Each output Port 2 is connected to the inputport 2 of the layer 2 diagonal switch in the next stage. (Diagonalconnections are so-called because they connect switches in differentrows and appear as diagonal lines in a schematic drawing of a network.)

Ringlet Connections to the Network.

The network supports either one or two ringlets connected to each row.If one ringlet is connected per row, it is connected to input and outputports 2 of the first and last stages of the network, and input andoutput ports 0 and 1 are each connected for packet recirculation. If tworinglets are connected per row, one is connected to input and outputports 2 of the first and last stages of the network, one is connected toinput and output ports 1 of the first and last stages of the network,and input and output ports 0 are connected for packet recirculation.

Enabled Input Port.

An enabled input port is a port that accepts input data consisting ofidles and/or packets. All information on disabled input ports isignored.

Enabled Output Port.

An enabled output port is a port to which packets may be routed. Apacket is never routed to a disabled output port.

Recirculation Port.

A recirculation port is a port that connects to a recirculation ringlet.

Recirculation Ringlet.

A recirculation ringlet is a ringlet that connects from an output stageswitch to an input stage switch on the same row and does not contain anyoperational nodes. The ringlet is purely to recirculate misroutedpackets from the output of the network back to the input so that thepacket can try to be routed again. Idles on recirculation ringlest areignored.

SUMMARY OF THE INVENTION

The standard IEEE Scalable Coherent Interface for data packettransmitting rings has a protocol for initializing individual ringlets.The invention extends that protocol across a network of switches by anordered transition of the network from its operational state through theTERMINATE, ABORT, STOP, RESETL and RESETH states back to its operationalstate in response to the receipt of ABORT, STOP, RESETL or RESETHpackets at the switches of the network.

BRIEF DESCRIPTION OF THE DRAWINGS

The invention is described by reference to the drawings in which:

FIG. 1 is a block diagram that illustrates the implementation of aswitching network, scrubber nodes and ringlets in accordance with theinvention, and

FIG. 2 is a block diagram that shows an implementation of the switchesof the switching network of FIG. 1.

TECHNICAL DESCRIPTION OF THE INVENTION Layered Network SwitchSpecification

Specifications for the Layered Network Switch are:

Summary of Restrictions

The Layered network assumes certain restrictions on the SCI ring inorder to implement all of the required SCI protocols. They are collectedhere for reference:

Scrubber Location

The scrubber must be located immediately after the Layered network andbefore any nodes in the ring. This implies that any node that contains ascrubber must have it located logically before the node. (A node thatviolates this restriction cannot be a scrubber, though it could be usedas a non-scrubber.)

SYNC Packets

If a node is the scrubber and also uses SYNC packets to train its inputport for skew, it must do so during initialization; it must not dependon receiving SYNC packets during normal operation.

Fair Only Nodes

Nodes must operate as fair only. Specifically, packets' command.mprfields are modified by the switch, and are generally set to zero by thenetwork just before arriving at their destinations. The network alwayssets idle.ipr and idle.It to zero in idles leaving the network.

Initialization.

The nodes must be either compatible with the SCI standard initializationsequence or go directly to operational mode without sending anyinitialization packets.

Resetting Two Ringlets Per Row

To assure identical reset phase for the nodes in a two-ringlets-per-rowconfiguration, both ringlet scrubbers in a row must be reset at the nodeinterface at the same time.

ClockStrobe Event00

The clock strobe option in SCI is not supported across the entirenetwork. This protocol depends on the SCI nodes being connected in aring, which is of course not true in the switched network. However, itis supported on an individual ringlet attached to the network. TheEvent00 has a targetID equal to the clock master in the ringlet and sowill be routed properly by the network. Since there is uncertainty inthe transit time through the network due to varying congestion the clocksynchronization may not be precise.

Broadcast

The broadcast option in SCI is not supported across the entire network.This protocol depends on the SCI nodes being connected in a ring, whichis of course not true in the switched network. However, it is supportedon an individual ringlet attached to the network. The Broadcast has atargetID equal to the Broadcast master (or one of the other nodes on thelocal ringlet for a broadcast resume) in the ringlet and so will berouted properly by the network.

Clocks and RESET

The clock and JTAG clock must be running while the RESET*I pin is active(reset is synchronous).

Special TargetID Packets

Packets with special targetID's (FFF0₁₆ -FFF7₁₆) are ignored anddiscarded by the network. They are replaced by idles. (These ID's arereserved by the SCI specification for future use, and are not nowdefined.)

Clear Packets

CLEARL and CLEARH (FFFA₁₆, FFFE₁₆) packets are ignored and discarded bythe network, and are replaced by idles.

Maximum Size Network

The size of time-out counters in the switch limit the network size toless than the SCI limit of 65,520 nodes--up to 2048 ringlets can besupported with the specified counter sizes. Future versions of theswitch can have larger counters.

Switch Block Diagram Description

The block diagram of the Layered network switch is shown in FIG. 2.

Elastic Buffer 20

Symbols enter the Elastic Buffers 20 which align their timing with theswitch's internal clock, detect packet boundaries and insert and deleteidles and SYNC packet symbols. The symbol from each of the ElasticBuffers 20 is first strobed into one of two internal registers accordingto the polarity of the SCI strobe. The two registers form the front endof a four-symbol FIFO that is normally kept half full. When the FIFOfills further, an idle or SYNC symbol is deleted to help empty the FIFO.When the FIFO begins to empty, an idle is inserted (duplicated) torefill it. The output of the FIFO is clocked into register unit 22.

In the packet detection logic 24, symbols are examined to distinguishpackets and idle symbols. If the symbol is the first one in a packet, itis further distinguished between an operational packet, aninitialization packet and an ABORT packet. If packets arrive with nointervening idles they are routed together, as if they were one packet.The switch will not insert an idle in this case. The output of thepacket detection logic 24 is supplied to the registers 26.

Initialization packets, recognized by their targeted values in the rangeFFF0₆ . . . FFFE₁₆ and a correct Cyclic Redundancy Check (CRC) providedby CRC calculation 28 serve to control the initialization state machine.Arrival of initialization packets is noted by packet type 44, but thepackets themselves are discarded.

ABORT packets are recognized by the unique flag pattern of the ABORTpacket immediately followed by a SYNC packet: 11111001₂, and by theirtargetid value of FFFB₁₆. (While there are 6 flag 1's in the ABORTpacket, some SCI node interface chips sometimes emit only 5 1's, whichis also recognized by the switch.)

STOP packets are recognized by their targeted value of FFFB₁₆ and acorrect CRC.

Configuration, Boundary Scan, Status 52

This information is supplied via the test port. It identifies thelocation of the switch in the network rows and columns and supplies theoutput to the claim Resolver 40 in a form that is convenient for use bythe claim Resolver 40, and provides for access to the switch's internallogic, and the interconnect between switches, for test and errorrecovery purposes.

Misroute Detect, Scrubber, Request Bits, Idle, Targetid Unit 24

Packets are marked for the several SCI protocol activities and therequest bits needed for routing are isolated and prepared for the claimresolver 40.

Initialization State Machine 44

When an ABORT, STOP or RESET packet is recognized the switch enters aninitialization sequence that is paced by a state machine 44 coupled toreceive inputs from the register units 22. State machine behavior isaimed at causing, and responding to, initialization protocols definedfor rings in the SCI standard.

CRC Calculator 28

The CRC for packets is checked in this block. The results of the checkare given to the next stage register 30.

claim Resolver 40

The two-bit route request values from the three input ports are comparedwith each other and the availability of output ports, and an allocationdecision is made for each. The decisions are sent to the outputMultiplexors 32 which supply the output registers 34, 36. When possible,all requests are satisfied by claiming requested output ports; wherenecessary an unrequested port is claimed. Only operational packetscompete for output ports, since initialization packets and idle symbolsare absorbed and regenerated.

Idle and Initialization Packet Generator 48

Idles and initialization packets are generated and made available to alloutput ports according to the state of the initialization state machine44 which supplies its output to the register 46. The idle andinitialization packet generator is in turn coupled to the register 50which have their outputs coupled to the multiplexor 32.

Output Multiplexors, CRC Stomp, Error Counts 32

The output port symbols are selected from four possible sourcesaccording to the initialization state machine 44 and the claim resolver40 results. Each of the three output multiplexors operates the same way.The possible selections are one of the three input ports' symbols or theinitialization/idle generator 48.

The output strobe is the same signal on all three ports. It is one halfthe frequency of the switch clock, and is clocked the same as the otheroutput port lines.

The multiplexors 32 also mark failed CRC's with a stomped value thatmarks the packet failure as previously detected. They also count thenumber of newly detected failures for later analysis and use by thefault control algorithms.

The JTAG port 52 is for test purposes and has configuration outputs onlines 54 to the register 38, and on line 56 to packet detection logic 24to supply network configuration. The JTAG port also is coupled to theinputs and outputs of the chip for boundary scan purposes, as indicatedby lines 58 and 60, respectively. The JTAG port 52 also obtains statussignals from the lines 62 to the elastic buffers, from the idle andinitialization packet generator 48 on the lines 64 and from themultiplexors on the lines 66.

Physical Layer Description

The physical layer connections consist of three input 19 and threeoutput 37 SCI ports, each containing 18 differential input and outputsignals, respectively. Each input port x consists of 16 data signals(SCIDIx₋₋ 0 . . . SCIDIx₋₋ 15), a flag bit (SCIFIx) used to delimitpackets, and a strobe signal (SCISIx) for latching incoming data. Eachoutput port x consists of 16 data signals (SCIDOx₋₋ 0 . . . SCIDOx₋₋15), a flag (SCIFOx), and strobe (SCISOx). Each 16-bit quantitytransferred is called a symbol and is clocked on each rising and fallingedge of the strobe signal. All 18 signals transition at the same timeevery 2 ns (500 Mega-transitions per second) giving an effective datatransfer rate of 1 Gbyte/sec. (The switch chip actually operates at 299Mega-transitions per second worst case.)

Packet and Idle Formats

The SCI standard contains a variety of packet formats. Only those formatdetails that affect the switch's behavior are discussed here. TABLE Ithrough TABLE V illustrate the packet and idle formats. For details notexplained here see the SCI specification (IEEE Std 1596-1992).

                  TABLE I                                                         ______________________________________                                        Send and Echo Packet Formats                                                  ______________________________________                                         ##STR1##                                                                      ##STR2##                                                                     ______________________________________                                    

                  TABLE II                                                        ______________________________________                                        Request-Echo Packet Format                                                    ______________________________________                                         ##STR3##                                                                      ##STR4##                                                                     ______________________________________                                    

                  TABLE III                                                       ______________________________________                                        Request Packet Format                                                         ______________________________________                                         ##STR5##                                                                      ##STR6##                                                                     ______________________________________                                    

                  TABLE IV                                                        ______________________________________                                        Symbol Groups                                                                  ##STR7##                                                                     ______________________________________                                    

                                      TABLE V                                     __________________________________________________________________________    Idle Symbol Encoding Format                                                    ##STR8##                                                                     __________________________________________________________________________

Send Packet Formats

Send packets, including request and response packets, are recognized bythe transition of the flag bit in the symbol stream to 1, by the factthat the symbol is not in the range FFF0₁₆ . . . FFFF₁₆, and by therepeat of the flag bit=1 in at least the second through fourth symbols.The value of the first symbol is called "targetid," and contains routinginformation used by the switch. When a send packet is recognized, partof the second symbol "command" is also decoded. In the first stage ifthe configuration-specified portion of targetid is not equal to the ringnumber specified by the configuration, then command.old is cleared tozero. The command.mpr field is also sometimes set by the switch. The endof a send packet is recognized by the transition of the flag bit to0--the packet ends 4 symbols after this occurs. The flag sequence is:111 . . . 10000. The CRC in the packet is checked for correctness.

Echo Packet Formats

Echo packets are recognized by the transition of the flag bit in thesymbol stream to 1, by the fact that the symbol is not in the rangeFFF0₁₆ . . . FFFF₁₆ and by a flag transition to 0 after a total of 3one's. Echo packets are 4 symbols long. When an echo packet isrecognized, part of the second symbol "command" is also decoded. In thefirst stage if targetid is not equal to the ring number specified by theconfiguration, then command.old is cleared to zero. The command.mprfield is also sometimes set by the switch. The flag sequence is: 1110.The CRC in the packet is checked for correctness.

Initialization Packet Formats

Initialization packets are recognized by the transition of the flag bitin the symbol stream to 1 and that the targetid value is in the rangeFFF0₁₆ . . . FFFE₁₆. Initialization packets affect the initializationstate machine. Except as specified below, CRC fields are checked forcorrectness.

ABORT Packet Formats

Whenever the flag bit is 1 in at least 5 adjacent symbols and 0 inexactly the two following symbols (that is, a flag sequence of . . .11111001), and by the targetid field=FFFB₁₆ then an ABORT packet andfollowing SYNC packet is recognized. The CRC field is zero and is notchecked.

SYNC Packet Formats

If the flag bit transitions to 1 in the symbol stream, the targetid isFFFF₁₆ and the next flag is zero, then a SYNC packet is recognized. Thepacket length is 8 symbols. The SYNC packet can occur in bothinitialization and operational states. The CRC field is zero and is notchecked.

STOP, RESET and CLEAR Packet Formats

These packets have the flag bit set in the first four symbols and clearin the last four. They are recognized by their targetid values and by acorrect CRC. Clear packets are ignored, discarded and replaced by idleswhen in operational mode, and by sync packets otherwise.

SpecialID Packets

These packets, with targetid's in the range FFF0₁₆ to FFF7₁₆, arereserved in the SCI standard but have no further definition. Becausetheir targetid does not specify the desired routing and their functionsare not known, the switch detects their sizes according to the normalflag protocol (the packet ends four symbols after the flag transitionsto 0) and converts them to idles. No CRC check is made.

Idle Symbol Formats

An idle symbol is transmitted whenever no packet is being transmitted.Idle symbols are generally discarded during input and regenerated asneeded during output, but some of the bits in the idle symbol are saved.During normal operation, every packet leaving the network is nearlyalways followed by at least one idle symbol. Idles may be missingbecause of deletion due to differences in clock frequencies and alsowhen packets arrive at a switch input port with no intervening idles.

Idles within the network carry additional information instead ofidle.ipr. However, these idles never leave the network.

Error Handling

The switch records error information that it detects for latertransmission via the Test Port 51. It also accepts configurationinformation via the Test Port for response to error conditions.

Initialization

This section documents the behavior of Layered network switches duringinitialization. The initialization process begins upon application ofpower and reset and continues until all ringlets have completed theirindividual initialization sequences.

The SCI standard (IEEE Standard for Scalable Coherent Interface, IEEEStd 1596-1992) provides five types of reset. The supported types arepower₋₋ reset and linc₋₋ reset; the unsupported types are warm₋₋ reset,command₋₋ reset and linc₋₋ clear. The network supports power₋₋ reset andlinc₋₋ reset and does not specifically support warm₋₋ reset, command₋₋reset and linc₋₋ clear. However, warm₋₋ reset and command₋₋ reset wouldlikely operate correctly with nodes that implemented them, since they donot appear to affect the network differently from the supported types;they affect internal node states rather than the network.

The Layered network is designed to operate with the scrubber as thefirst node after the network in each ringlet. The initializationsequence takes this into account; neither initialization nor normaloperation will behave properly if the scrubbers are in other locations.

Ringlet Reset Scenario

In a simple ringlet without a Layered network involved, reset occurs intwo stages. First, the nodes cooperate to place themselves in a definedstate, and then ringlet software modifies the state to that desired forsystem operation. With a Layered network, initialization begins withswitch configuration via the Test Port before the SCI initializationsequence can proceed.

Notification of Reset for Ringlet Nodes

A reset process begins at one or more nodes as an external signal. Ascrubber node that is reset responds by sending out ABORT, SYNC andRESETH packets. A non-scrubber node that is reset begins sending outABORT, SYNC and RESETL packets. Once a RESETH packet is received thenon-scrubber node switches to sending RESETH packets. Thus, since thescrubber is the first node in the ringlet, the appearance of RESETH atthe network implies that all nodes on the ringlet are in the resetstate.

When an SCI node interface chip is reset by its reset pin, it beginswith its reset phase PH=0 and ends the initialization sequence with PH=1. When it is reset by a reset packet its phase is unchanged; it endswith PH toggled. The SCI standard also specifies PH=0 upon power up.

Scrubber Assignment

The network requires that the scrubber be located as the first nodeafter the network in each ringlet. Therefore the SCI standard scrubberassignment algorithm is not necessary and the network does not supportit. Instead, the fixed scrubber assignment option is supported.

Operational Node ID Assignment

Each ringlet's nodes will have an initial assigned node ID that isunique within the ringlet, but is not unique in the system. (In fact,all of the scrubbers have the same ID.) Each node must therefore have ameans of changing that ID to a system operational ID before it can beginnormal operation, perhaps some form of software-controlled bootstrapsequence. The operational ID must have the ringlet number in thesystem-defined position. The SCI node interface chip's operational IDcan be set from control and status register (CSR) writes.

Initialization Packets

Initialization packets have their targetid values all in the rangeFFF8₁₆ to FFFF₁₆. They are specially recognized by the nodes and by theswitches. The packets and idle symbols of interest, as generated by theswitch, are given in TABLE VI.

                                      TABLE VI                                    __________________________________________________________________________    Initialization Packet Values                                                         Symbol                                                                            Symbol                                                                            Symbol                                                                            Symbol                                                                            Symbol                                                                            Symbol                                                                            Symbol                                                                            Symbol                                     Packet type                                                                          0   1   2   3   4   5   6   7                                          __________________________________________________________________________    ABORT  FFFB.sub.16                                                                       FFFB.sub.16                                                                       FFFB.sub.16                                                                       FFFB.sub.16                                                                       FFFB.sub.16                                                                       FFFB.sub.16                                                                       0000.sub.16                                                                       0000.sub.16                                STOP   FFFB.sub.16                                                                       FFEE.sub.16                                                                       0000.sub.16                                                                       0000.sub.16                                                                       0000.sub.16                                                                       0000.sub.16                                                                       0000.sub.16                                                                       9BCD.sub.16                                SYNC   FFFF.sub.16                                                                       0000.sub.16                                                                       0000.sub.16                                                                       0000.sub.16                                                                       0000.sub.16                                                                       0000.sub.16                                                                       0000.sub.16                                                                       0000.sub.16                                RESETH 0                                                                             FFFC.sub.16                                                                       FFEF.sub.16                                                                       FFFF.sub.16                                                                       FFFF.sub.16                                                                       FFFF.sub.16                                                                       FFFF.sub.16                                                                       FFFF.sub.16                                                                       161D.sub.16                                RESETH 1                                                                             FFFD.sub.16                                                                       FFEF.sub.16                                                                       FFFF.sub.16                                                                       FFFF.sub.16                                                                       FFFF.sub.16                                                                       FFFF.sub.16                                                                       FFFF.sub.16                                                                       537E.sub.16                                RESETL 0                                                                             FFF8.sub.16                                                                       FFEE.sub.16                                                                       0000.sub.16                                                                       0000.sub.16                                                                       0000.sub.16                                                                       0000.sub.16                                                                       0000.sub.16                                                                       5468.sub.16                                RESETL 1                                                                             FFF9.sub.16                                                                       FFEE.sub.16                                                                       0000.sub.16                                                                       0000.sub.16                                                                       0000.sub.16                                                                       0000.sub.16                                                                       0000.sub.16                                                                       110B.sub.16                                Idles with                                                                           02FD.sub.16                                                                       --  --  --  --  --  --  --                                         no go bits*                                                                   Idles with                                                                           0EF1.sub.16                                                                       --  --  --  --  --  --  --                                         go bits                                                                       (normal                                                                       idles)*                                                                       __________________________________________________________________________     *These values follow the values of the idles arriving on the input ports.

System Reset Sequence

"When a node is reset or cleared, it initially outputs an ABORT packetimmediately followed by a SYNC packet . . . " (SCI standard, section3.10.8). In other words, a reset sequence always begins with anABORT/SYNC packet sequence. However, if there are more than one node inthe ringlet, subsequent nodes might not repeat the ABORT if they are notout of synchronization; instead they begin with a STOP and/or a RESETpacket sequence. In a ring, this causes all nodes to be initialized, andin a Layered network system this causes all ringlets to be initialized.It is not necessary to provide many individual reset signals in order toreset the system.

Upon detection of an ABORT, STOP, RESETL or RESETH packet, the switchenters initialization state. Abandoning all other activity, it generatesABORT, STOP, RESETL and RESETH packets and idle symbols on all outputports in a timely manner as described below. This has two effects:first, the existence of a reset state somewhere in the system isbroadcast to all ringlets, causing their scrubber nodes to enter resetstate. Second, the network waits until all ringlets have propagatedtheir normal idle symbols, that is, all ringlets have synchronized theirreset activity.

To implement the above scenarios, the switches must properly processinitialization packets. Each packet received generally has lots of SYNCpackets between them; the SYNC packets are broadcast in like quantityafter each broadcast of another kind of packet. Except as specifiedotherwise, all stages of switches in the network behave the same way forthe ports that are not recirculation ports. Initialization packets onrecirculation ports are usually ignored (see TABLE VII). Note that oncethe initialization sequence is started it must be completed to get theswitch back to operational state.

                                      TABLE VII                                   __________________________________________________________________________    Switch Initialization State Machine Behavior                                  State    Output Behavior Exit Condition and State                             __________________________________________________________________________    OPERATIONAL                                                                            Follow input idles on all active non-                                                         On any Abort, Stop or Reset packet,                           recirculation input ports whenever                                                            go to Terminate state.                                        no packets are being sent                                            TERMINATE                                                                              Terminate any current packets by                                                              On an Abort on an enabled input go                            bringing Flag low and sending five                                                            to Abort state. Otherwise on a Stop                           or six idles.   on an enabled input go to Stop state.                                         Otherwise on a Reset on an enabled                                            input go to Resetl state.                            ABORT    Broadcast one ABORT packet and                                                                On any Stop on an enabled input go                            1023 or more SYNC packets.                                                                    to Stop state. Otherwise on any                                               Reset on an enabled input go to                                               Resetl state.                                        STOP     Broadcast sets of one STOP packet                                                             On a Reset on an enabled input go to                          and 1023 SYNC packets.                                                                        Resetl state.                                        RESETL   Broadcast sets of one RESETL                                                                  On a Reseth packet on each enabled                            packet and 1023 SYNC packets.                                                                 non-recirculation input port go to                                            Reseth state                                         RESETH   Broadcast sets of one RESETH                                                                  On idles arriving on all enabled non-                         packet and 1023 SYNC packets.                                                                 recirculation input ports go to                                               Flush.sub.-- Reseth state.                           FLUSH.sub.-- RESETH                                                                    Broadcast normal idles on all output                                                          On idles arriving on all enabled input                        ports. Follow input idles on all                                                              ports go to Operational state.                                enabled non-recirculation input                                               ports whenever no packets are                                                 being sent.                                                          __________________________________________________________________________

Operational

The switch is normally in OPERATIONAL state; it begins operation thereupon chip reset (not SCI reset) so it may be used with node interfacesthat do not implement the SCI initialization protocol. The switch usesthe merged input idles from all active non-recirculation input ports oneach output port whenever there is no packet being transmitted.

TERMINATE

Upon receipt of an input packet condition causing initialization, theswitch pauses in TERMINATE state to terminate current packets, if any.Then it proceeds to the state dictated by the incoming packet. Five orsix idles are sent so that the strobe on the first symbol of thefollowing initialization packet will be high.

ABORT

While in ABORT state the switch broadcasts ABORT and SYNC packets to alloutput ports (including those previously sending other kinds ofpackets). Any additional ABORT packets arriving while the switch is inABORT state are ignored. The switch recognizes STOP and RESET packetswhile in abort state.

STOP

A switch in ABORT state or TERMINATE state and recognizing a STOP packetenters stop state after completing its current series of SYNC packets oroperational packets, respectively. While in STOP state, it repeatedlybroadcasts a STOP packet to all output ports followed by a series ofSYNC packets. The switch recognizes RESET packets while in STOP state.

RESETL

A switch in RESETL state broadcasts a RESETL packet, of the phasedescribed below, on its output ports followed by a series of SYNCpackets. It continues to broadcast RESETL and SYNC packets until allenabled non-recirculation input ports have received a RESETH packet.(This may happen immediately, for example when the ringlets have onlyscrubber nodes.)

The network is designed to reset upon occurrence of a single resetstimulus anywhere in the system. Upon power₋₋ reset and nodeinitialization, the SCI node interface chips issue RESETL0 or RESETH0,if reset later by a reset packet they will alternately issue RESETL1 orRESETH1 and RESETL0 or RESETH0. Except at power up, the scrubbers willnot all have the same phase. In the interest of accepting the latestreset request, the phase of the last reset arriving on any input port isused.

RESETH

A switch in RESETH state broadcasts a RESETH packet, of the same phaseas the latest input RESET packet, and a set of SYNC packets on itsoutput ports. It continues to broadcast RESETH and SYNC packets untilall enabled non-recirculation input ports have received an idle.

FLUSH RESETH

A switch in FLUSH₋₋ RESETH state broadcasts idles while waiting for theidles to arrive at the recirculation port(s), if any. These idles havego bits, idle.ac, idle.cc and idle.old set according to the incomingidles in the same way as during normal operation. This state looks muchlike normal operation, except that all switches ignore RESET, STOP andABORT packets.

SYNC Packets

A switch recognizing a SYNC packet, in any initialization or operationalstate, deletes/strips it, effectively treating it as if it were idles.Note that SYNC packets can also occur at times other thaninitialization; they are optionally (not by the switch) used forcalibration of the link level media. If a node wishes to be the scrubberand also use SYNC packets to train its input port for skew, it must doso during initialization; it must not depend on receiving SYNC packetsduring normal operation.

Normal Operation

During normal operation the Layered network switch routes incomingpackets to output ports according to their targetid values. It resolvesconflicting requests to properly route as many of them as possible,routing any remaining requests on the remaining ports.

The switch recognizes send and echo packets in order to determine whenthey end so that the port can be re-used. It checks CRC values and notesand stomps any errors. (Error information is available to a JTAGcontroller.)

Routing Algorithm

The first priority in the routing algorithm is completion of packetsthat have already been routed. No packet (except for the initializationsequences) can displace a packet that started earlier. Output ports inuse by already-routed packets, and output ports that are disabled, areunavailable to the simultaneous routing algorithm below.

The two bits from each packet targetid are selected and conditionallycomplemented according to the Bit₋₋ Select and Complement configurationinformation scanned in from the test port 51. The input ports' requestsare assigned in order--port 0, port 1 and port 2. The first conditionsatisfied in the following list results in assignment:

If output port 2 is requested and available.

If output port 1 is requested and available.

If output port 0 is available.

If output port 1 is available.

If output port 2 is available.

Once assigned, the output port is unavailable for the other simultaneousrequests.

Because some requests exit on unrequested ports, they can exit thenetwork to an unrequested ringlet. These requests are called "misrouted"and, since their targetid's are not recognized in the ringlet, will passthrough and arrive again at the network. They are repeatedly routeduntil they arrive on the requested ringlet.

Note that a packet may or may not be ultimately misrouted if anunrequested port is assigned, since there are often opportunities inlater stages of the network to compensate for the unrequested route.

Routing of Back-to-back Packets

The idle symbol following a packet is included in the routing of thepacket through the switch. The reason the idle is included with a packetis to prevent the switching of packets from creating back-to-backpackets. If we allowed switching to create back-to-back packets thenlong strings of back-to-back packets could be generated via therecirculation ports. If the string were long enough the SCI nodeinterface chips would eventually lose sync due to a lack of idles toinsert/delete. Back-to-back packets are created when a switch needs todelete an idle and there is only one idle between packets. If packetsare back to back (including packets that end prematurely with a newpacket) then they are routed together on the same output port. If apacket immediately follows a specialID packet it will also be convertedto idles along with the specialID packet. When packets are routedtogether the trailing packets are likely to be misroutes since theyprobably won't have the same targetid. When the back-to-back packetsreach an SCI node interface chip it will usually separate the packets byan idle before they return to the network.

Bandwidth Allocation Protocol

This section documents the behavior of the Layered network with respectto standard SCI bandwidth allocation. Several SCI assumptions about ringbehavior do not directly apply to the Layered network, so that carefulprotocol analysis and network behavior are necessary, particularly inthe area of bandwidth allocation.

The SCI assumption of ring connection is that there is assurance thatsymbols arrive in the same order as they were sent (though more elementsmay be inserted in between), no matter what part of the ring isinspected. The standard discusses interconnection of multiple ringsusing "agents" that remove data that is addressed outside the ring,completely follow the protocol on the sending ring, and then send thedata on another ring, following the receiving ring's protocol. An agentthus appears like a node to the ring; it follows all the protocol. Whendiscussing agents, the SCI standard sometimes refers to the associatedrings as "ringlets." Transfer of data between ringlets is considered outof the standard's scope.

Bandwidth Allocation in the Ring

In order to prevent starvation of nodes trying to access the ring, SCIprovides bandwidth allocation mechanisms. Information about ring statusis communicated in idle symbols as follows (IEEE 1596-1992, section3.2.11):

Priority--idle.ipr distributes the best current estimate of theringlet's highest priority.

Allocation Count--idle.ac changes in value when all nodes have had anopportunity to transmit a send packet.

By observing changes in idle.ac, a ring node can assure itself that anaddressed node has had an opportunity to respond to a request, at leastas far as competing ring traffic is concerned. This assurance depends onthe fact that the order of transmission of packets and idle symbolvalues is never changed.

Circulation Count--idle.cc measures the time taken to travel around thering. A change in value of idle.cc is a token that notes the completionof a trip around the ring.

By observing changes in idle.cc, a ring node can assure itself that apacket has had time to reach its destination on the ring and its echo toreturn. If the echo doesn't return, the node can declare an errorsituation.

Go bits--idle.hg and idle.lg are the high priority and low prioritybandwidth allocation control flags. They enable allocation inapproximate round-robin order.

Old bit--idle.old, is used in conjunction with idle.hg and idle.lg. Itis set by the scrubber and cleared by any node that is currently usingthe network. If idle.old remains set and the go bits remain clear, thenetwork protocol is violated.

Low-type--idle.lt specifies the idle's priority class and which nodescan consume it without accumulating debt.

Extension to the Switched Network

The Layered network and the ring can be married as shown in FIG. 1.Symbols progress through the ring, through the network and back to thering. Samples of different ringlet populations are shown. Ringlet 0 has3 nodes, ringlet 1 has two nodes, and the rest have one node each. Thescrubber is labeled S and is the first node encountered in each ringlet.The scrubber must be logically located before the first node.

For a straight setting of the switches, the ordering assumptions of theSCI standard are satisfied; no reordering is necessarily performed bythe network. However, if the switches are dynamically changed it isclear that spurious changes might be introduced in idle symbol bitvalues. Also, it can happen that multiple packets are simultaneouslysent to the same network output terminal, creating an overload on thatterminal or on switches leading to the terminal. One possible resolutionof this situation is to queue the extra packets, but this leads toadditional serious problems (tree saturation, hot spots, FIFO queues addto switch complexity, etc.), and the preferred solution is to send theextra packets on different, and wrong, rings. The time they spend goingaround the wrong ring has the same effect as queuing them, but withfewer bad side effects; they try again each time they go through thenetwork. The extra time also effectively changes the order of packets(if, in a parallel system, there was a definable order in the firstplace), so that the assumptions about symbol order behavior areviolated. The protocols described here are aimed at restoring this senseof ordering so that any individual node's view of the protocol appearsto be that of the ring.

System Constraints

In order to provide tractable mechanisms for meeting SCI protocols, thenetwork architecture places constraints on some aspects of systemconfiguration.

System Addressing

The network uses a few of the bits in the SCI node ID to determine itsrouting. Therefore node ID's must be assigned so that those bits areconsistent with the node's position in the system. The bits that areused are selected as part of the network design process, and arecollectively called the ringlet number. Typically, in a system with Nringlets, the most significant n (log₂ N) bits are used for the ringletnumber. (Full agents typically use similar addressing methods.) However,the switch design is such that any of the SCI node ID bits can be usedfor routing--they do not need to be contiguous nor do they need to startin any special bit position.

Scrubber Locations

The scrubber in a SCI ring alters several of the bits that affect packetcontrol. These bits must also be interpreted by the network switches,and that interpretation requires that each ringlet's scrubber be locatedimmediately after the network. (This is a constraint not required with afull agent switch.)

Ringlet Priority

The network must mark packets to detect their misroute age in order toimplement the idle.cc protocol. This is done by setting new (command.oldis zero) packets' priority fields (command.mpr) to specific values. Thisaction overrides any priority values placed there by nodes when theysend or pass the packets. As a packet exits from the network to thecorrect ringlet, the network clears command.mpr to zero. (The network isdesigned only for use with fair-only nodes, that is, with node.spr=0.Values of 1-3 are replaced as the packet goes through the network andtherefore would not have their intended effect.)

Priority is typically used to more closely manage the utilization of aheavily-loaded ring. In a system with a network there is much morefreedom to configure the system to avoid heavy loading of any ringlet,so the priority feature is less important. Nodes are more likely tooperate satisfactorily without using unfair protocol.

Expansion of Bandwidth Allocation to the System

Nodes constructed for use in SCI rings expect to see ring protocolbehavior. When the network is added to a system, the individual nodeview of system behavior must be preserved. This section introducespreservation conditions before misrouted packets are considered (theywill be included in the next section).

Significant Behavior of idle.cc and idle.ac

These bits of the idle symbol are defined so that, in a correctlyimplemented ring, their values change once each time they travel aroundthe ring. Specifically, each node copies the values from incoming idlesto outgoing idles, unchanged except for a single distinguished node(called the scrubber) which copies the complement of the incomingvalues. Since packets do not get reordered with respect to this bitcopying protocol, a sending node can observe the values of these bits todetermine when a packet has had time to get to anyplace on the ring.

The idle.cc bit follows the above behavior as described, always copyingthe bit value immediately (its travel is of course held up by nodessending packets, since no idle symbols then exist to propagate thevalue). The idle.ac bit follows the above behavior as described, exceptthat the idle.ac bit is not copied by a node if it is trying to transmitbut cannot due to the protocol. Instead, it continues to send idles withthe previous value of idle.ac until it has successfully transmitted thepacket and received its echo. Thus another node can watch idle.ac and,once it changes, be assured that all nodes have had a chance to transmitto their reserved destinations.

Because of the definition of these bits, certain behaviors, such asidle.ac changing faster than idle.cc, are impossible in a correctlyoperating ring. The SCI node interface chip recognizes occurrence ofsome of these impossibilities as error conditions and shuts the systemdown.

Expansion of idle.cc and ac

Expansion is nearly identical for idle.cc and idle.ac, so in thefollowing both are called idle.xc. If idle.xc is allowed to propagate inan uncoordinated way into the ringlets, there will be many instances ofpackets and idle.xc bits being reordered from the nodes' viewpoints. Thenetwork solution is to assure that all idle.xc instances of the samevalue (one from each ringlet) have arrived in the network before any ofthem are allowed to propagate out of the network. These delays make thenetwork look possibly larger than it physically is, and packets can getahead of their corresponding idle.xc changes. But idle.xc does not getahead of corresponding packets, so no node time-out error conditions aretriggered.

Expansion of idle.ipr, hg, lg, old and lt

The network is designed for propagation in the context of fair protocol.These bits are set in output idles as follows:

ipr--idle priority, which is a measure of ringlet priority, is set tozero in every idle leaving the network. While unfair capable nodes maycause higher priorities to be placed in idle.ipr, they also are placedin command.mpr which would confuse the misroute packet protocol (below).The system constraint to priority level 0 avoids this confusion, sincethe nodes won't increase command.mpr. (Since packets are typicallychanging from one ringlet to another, ringlet priority is not verymeaningful.)

hg and lg--As the ringlet gets busier, the available go bits arereduced, causing nodes to delay introducing new traffic. (If for somereason go bits are lost completely, no traffic is possible.) To judgethe busy-ness of the entire network, switches OR the incoming go bitsfrom enabled non-recirculation ports to determine the outgoing go bitvalues. (Go bits are cleared by nodes to inhibit other node'stransmission. If these bits were ANDed, the system would soon run out ofgo bits and go to sleep.)

old--To assure that idle.old does not signal a protocol violation ifthere is activity anywhere in the system, the switches AND the incomingidle.old bits from enabled non-recirculation ports to determine theoutgoing idle.old values.

lt--the low-type bit is cleared to zero. The network only handles fairnodes and so it generates all high-type idles.

Misrouted and Stale Packets

The self-routing behavior of packets going through Layered networkswitches results in some packets going through the wrong ports, as faras their desired destination is concerned.

A stale packet is one that was misaddressed by the system software. Itimplies that there is a system error of some form, and is not expectedto enter into performance issues. It is only necessary that it becorrectly identified and processed. SCI defines a special echo thattells the sender what happened, and the network need only route thestale packet to its destination ringlet and then to any ringlet so thatit can be tossed by the latter ringlet's scrubber.

Packets can be misrouted for any of several reasons. Occasionally thepaths needed through the network are busy with other traffic. More oftenthere are several packets going to the same node; only one can becorrectly routed at a time, and the others are misrouted. These packetsincrease the traffic in the network; they can also end up arriving outof order with respect to nearby idles. The latter is undesirable becauseit violates assumptions on which SCI protocol is based. Thus, idle.ccand idle.ac must be held up if misrouted packets left the network aheadof them, until the packets return and are correctly routed.

Network Protocols

Protocols are defined for use within the Layered network so that SCIprotocols may be preserved in the attached ringlets. They interrelatethe advancement of idle symbol control bits to avoid misordering symbolsfrom the viewpoint of the ringlet nodes. They necessarily use extensionsof the SCI protocol.

SCI protocol is violated if idle.cc changes too often, that is, fasterthan the time to send a packet and receive its echo. To avoid this, thenetwork delays the change of output idle.cc values until all ringletshave propagated the change into the network. All idle.cc propagation issynchronized to this degree. The SCI algorithm always refers to changesin values of idle.cc, that is, a zero/one transition has the samemeaning as a one/zero transition. For simplicity in the network,however, idle.cc values are synchronized rather than their changes invalue, that is, all output idle.cc bits will become zero and will becomeone at effectively the same time.

If idle.cc does not change, nodes that are waiting for lost echoes willwait forever and their corresponding queue reclamation and other errorrecovery mechanisms will not be invoked. If idle.cc is changed veryslowly, there is no assurance that an improbable but possible extendedmisroute pattern will cause protocol violation. Also, idle.ac would haveto toggle slowly; this causes undesirable waiting in the queuereservation protocol.

SCI protocol is violated if idle.ac changes faster than idle.cc. Idle.acis supposed to proceed in the same manner as idle.cc, sometimes beingslowed by blocked nodes. The network avoids this violation by allowingthe network idle.ac outputs to change only after all idle.ac inputs havechanged and only when idle.cc is also changing.

SCI protocol is violated if a packet moves more slowly than idle.cc oridle.ac. The network avoids this by allowing all misrouted packets, thatoriginally arrived before the input idle changed, to be properly routedbefore allowing the output idle.cc (and therefore idle.ac) to change.

The Misrouting Algorithm

This section is explanatory in nature. It describes network behavior asa consequence of the switch behavior that is specified in othersections.

The SCI protocol controls idle.xc, (idle.cc and idle.ac) transitions byhaving the scrubber complement its value as it passes through while allother nodes pass it unchanged. These values' changes are used to detectlost packets (a kind of time-out) and other protocol violations.Therefore the misrouted packets must be allowed to arrive at theirdestinations after at most one idle.xc transition is made. Themisrouting algorithm assures that idle.cc transitions do not get aheadof packets by holding the transitions up whenever preceding packets aremisrouted and therefore delayed. Protection for idle.ac changes isaccomplished by observing from its definition that idle.ac cannotproceed faster than idle.cc. The network does not allow idle.ac tochange unless idle.cc also is changing; then idle.ac changes one cycleafter idle.cc.

When an unmarked packet arrives at the network it is marked with thelast state of idle.cc received on that port, which corresponds to thestate of idle.cc when the packet was created. If the packet is notmisrouted, its relationship with surrounding idles remains essentiallythe same, and the SCI protocol is preserved. If the packet is misrouted,it proceeds on whatever node or recirculation path it does reach,arriving again soon at the corresponding input port. The first stagerecognizes the misrouted packet and broadcasts a warning to all of thefinal stage switches, using idle symbols, and the final stage switchesreset their "stability" counters. The reset inhibits any change in thevalue of the idle.cc (and therefore idle.ac) bits in exiting idles untilenough time has expired for the misrouted packet to be correctly routed.This process is repeated until all similarly marked packets are routed.

The stability counters are set with a counting value large enough that asuccessful countdown implies that all packets marked with the old valueof idle.cc have been routed. Thus, the expiration of any one of them,and its corresponding change in output idle.cc, implies that the entirenetwork is free of such misrouted packets. When an input port recognizesthe new value of idle.cc, it broadcasts that fact, in "cc₋₋ done" idles,that cause all final stage switches to immediately change their outputsto the new idle.cc value.

It is conceivable, perhaps through an unrelated protocol error, thatdifferent output stages could be sending different values of idle.cc,and that the values have all propagated to the network inputs withouttriggering cc₋₋ done. Then at some point in every path through thenetwork there would be a switch seeing disagreeing idle.cc values in itsinputs, and no further changes would occur. To recover from thissituation, all switches (except the last stage ones) use their stabilitycounters to watch for idle. cc changes and warnings. If neither occurs,the switches force idle,cc to 0 everywhere by broadcasting cc₋₋ done(0)idles. (They also record this as an error condition.) The network existsin the following allowable states (Individual switches are not aware ofthe network state. They contribute to management of network state basedpurely on local information.):

S0: All stage n (last stage) outputs are emitting idle.cc=0 and thereare no misrouted packets circulating.

S1: All stage n outputs are emitting idle.cc=1 and there are nomisrouted packets circulating.

S0m0: All stage n outputs are emitting idle.cc=0 and there are one ormore 0-misrouted packets circulating. In S0 state, the ringlet scrubbersare converting idle.cc values from zero to 1. Therefore, new misroutesare being marked as 1-misroutes. All 0-misroutes are older than the new1-misroutes. All 0-misroutes must be correctly routed before switchingto the S1 state. And similarly for the S1 state.

S0m1: All stage n outputs are emitting idle.cc=0 and there are one ormore 1-misrouted packets circulating.

S1m0: All stage n outputs are emitting idle.cc=1 and there are one ormore 0-misrouted packets circulating.

S1m1: All stage n outputs are emitting idle.cc=1 and there are one ormore 1-misrouted packets circulating.

S0m0m1: All stage n outputs are emitting idle.cc=0 and there are one ormore 0-misrouted and 1-misrouted packets each circulating.

S1m0m1: All stage n outputs are emitting idle. cc=1 and there are one ormore 0-misrouted and 1-misrouted packets each circulating.

Note: The states intentionally do not provide for simultaneous emissionof different idle.cc values. While such a state will exist temporarily,it is not significant to understanding the state diagram, and willdisappear as soon as the idles carrying state information (cc₋₋ done)all reach the last stage and/or the stability periods subsequentlyexpire.

A state table is given in TABLE VIII. The table shows the allowabletransitions and the conditions that cause them. Note that changesbetween S0xx and S1xx states only occur if some stability counter hasexpired (expiration is broadcast to the network via cc₋₋ done idles).Due to construction of the algorithm, this can only occur when there areno 0-misroutes and no 1-misroutes, respectively, in the ringlets.

                                      TABLE VIII                                  __________________________________________________________________________    Network State Table                                                                                            Next                                         State State Change Condition     State                                        __________________________________________________________________________    S0    All input idle.cc values = 1 and any stability counter                                                   S1pires                                            A 0-misroute is detected   S0m0                                               A 1-misroute is detected   S0m1                                         S0m0  A 0-misroute is detected   S0m0                                               A 1-misroute is detected   S0m0m1                                             All 0-misroutes are serviced                                                                             S0                                           S0m1  All input idle.cc values = 1 and any stability counter                                                   S1m1res                                            A 0-misroute is detected   S0m0m1                                             A 1-misroute is detected   S0m1                                               All 1-misroutes are serviced                                                                             S0                                           S0m0m1                                                                              A misroute is detected     S0m0m1                                             All 0-misroutes are serviced                                                                             S0m1                                               All 1-misroutes are serviced                                                                             S0m0                                         S1    All input idle.cc values = 0 and any stability counter                                                   S0pires                                            A 0-misroute is detected   S1m0                                               A 1-misroute is detected   S1m1                                         S1m1  A 0-misroute is detected   S1m0m1                                             A 1-misroute is detected   S1m1                                               All 1-misroutes are serviced                                                                             S1                                           S1m0  All input idle.cc values = 0 and any stability counter                                                   S0m0res                                            A 0-misroute is detected   S1m0                                               A 1-misroute is detected   S1m0m1                                             All 0-misroutes are serviced                                                                             S1                                           S1m0m1                                                                              A misroute is detected     S1m0m1                                             All 0-misroutes are serviced                                                                             S1m1                                               All 1-misroutes are serviced                                                                             S1m0                                         __________________________________________________________________________

Misroutes are detected by the first stage switches.

To implement the network state behavior, the switches follow thealgorithms described in the following sections.

Initialization of idle.cc and idle.ac Values

The initialization process clears all idle.cc and idle.ac values tozero. Eventually all network inputs, having propagated throughscrubbers, will therefore become set to one.

Arrival of Packets and Idles from Ringlets

The first stage switch receives packets and idles from the attached SCIringlets. When idles are arriving the switch copies the values ofidle.cc and idle.ac to internal registers so that they are alwaysinternally available. The switch responds to the values in the idle asfollows:

When the incoming value of idle.cc changes on any enabled,non-recirculation port, the switch broadcasts cc₋₋ done idles (see idleformat, TABLE X), with the old idle.cc value, to all of its outputports. When an output packet already occupies a port, the cc₋₋ done idleis sent after the packet. The current idle.cc value is itself updatedwhen all incoming (enabled, non-recirculation) idle.cc values agree.

The value of idle.ac used in output packets is that of the most recentagreed-upon incoming values in idles from enabled, non-recirculationports.

When packets are arriving, the switch routes them to correspondingoutputs. It also checks command.old and compares the target address withthe ringlet number to distinguish between stale and other packets. Stalepackets are routed without further changes. Other packets are checkedfor age:

If command.old is clear, the packet is a new one from the ringlet, andit is marked by placing a value corresponding to the last received valueof idle.cc on that port in the command.mpr field. command.mpr isavailable for use because the system is restricted to fair only.

                  TABLE IX                                                        ______________________________________                                        Marking new packets                                                                   command.mpr                                                                   decimal binary                                                        idle.cc                 bit 0  bit 1                                          ______________________________________                                        0         2             1      0                                              1         3             1      1                                              ______________________________________                                    

If command.old is set the packet was previously misrouted or stale inthe network and must be routed again. If targeted isn't equal to theringlet ID, the packet was misrouted, so command.old is cleared and themisroute is announced via a broadcast misroute idle (see TABLE X).Again, if a packet already occupies an output port, the misroute idle issent after the packet. Otherwise the packet is stale, command.old is notchanged and misroute idles are not broadcast. The broadcast guaranteesthat each output port transmits the misroute idle at least once.

An SCI idle consists of a data byte and a parity byte. Within thenetwork, the idle format is modified according to TABLE X:

                                      TABLE X                                     __________________________________________________________________________    Network idle formats                                                              SCI              Network                                                  bit symbol                                                                             Standard description                                                                      symbol                                                                              Description                                        __________________________________________________________________________    0   ipr(0)                                                                             Best current estimate of                                                                  misroute                                                                            1 => a misrouted packet                                     ringlet's highest priority                                                                      has arrived at the first                                                      stage                                              1   ipr(1)                                                                             Best current estimate of                                                                  cc.sub.-- done                                                                      1 => a stage n stability                                    ringlet's highest priority                                                                      counter has expired                                                           (implying that there are no                                                   misrouted packets marked                                                      with the opposite value as                                                    viewed by the first stage                                                     switches of idle. cc in the                                                   system). The stabiiity                                                        counter expiring causes                                                       idle.cc to toggle. The                                                        toggle propagates through                                                     the ringlet (the scrubber                                                     inverts the toggle) and                                                       appears at the first stage.                                                   The first stage switch                                                        detects a toggle in idle.cc                                                   and generates cc done.                             3   cc   Circulation count                                                                         cc    Circulation count, and                                                        parameter for cc done                              2,4-     SCI standard definitions                                                                        SCI standard definitions                           15                                                                            __________________________________________________________________________

Transfer of Packets and Idles Through Switches

Intermediate stage switches propagate, in idles, their input ports'agreement on idle.cc and idle.ac values. They ignore the misroutemarkings on packets. When all enabled, non-recirculation input idle.cc'sagree then all subsequent output idle.cc values equal the agreed-uponvalue, otherwise the previous output idle.cc value is used. When allenabled, non-recirculation input idle.ac's have made a transition to anew value then all subsequent output idle.ac values equal the new value,otherwise the previous output idle.ac value is used. The followingapplies to all switches including the first stage. idle.ac transitionsare accumulated and further transitions are ignored until all enabled,non-recirculation inputs have made a transition to the new value and alloutputs have transmitted the current value of idle.ac at least once, sothat idle.ac can resynchronize across the network in case an idle.acchange straddles an idle.cc change. The idle.ac change can straddle theidle.cc change because the node's can hold up idle.ac independent ofidle.cc. The final propagation of agreement on idle.ac may start just asthe cc stability period is about to expire. Then, differential delays ofidle.ac in the network can cause some last stage switches to changeidle.ac and others to not change idle.ac when the stability periodexpires. On the next idle.cc change the last stage switches that did notchange idle.ac the last time will change and all of the last stageswitches will now have the same value of idle.ac. Looking at simpleinput agreement would not provide for resynchronization because thechanged idle.ac's would block agreement when they met the old idle.ac'sat a switch. The switch guarantees that a new value for the outputidle.ac is transmitted at least once on each output port. Transmittingon each output port makes sure that all switches see all transitions ofidle.ac so that the network can resynchronize if necessary. No suchguarantee is needed for idle.cc since cc₋₋ done is used forresynchronization.

Whenever the input idle.cc values disagree, the stability counter isrunning; when they agree, the stability counter is reloaded. "Stabilitycounter" refers to the counter's function in a stage n switch. In otherswitches, as discussed here, the counter is used to detect permanentidle.cc disagreement. If the stability counter completes its count time,the event is recorded in Permanent₋₋ cc₋₋ disagree and cc₋₋ done(0) isbroadcast to resynchronize idle.cc across the network. This detectspermanent idle.cc disagreement on the inputs should it occur.

Whenever a cc₋₋ done or misroute idle is received on a non-first stage,enabled input port, that idle is broadcast on all output ports (waitingfor packets if necessary). Because idle.cc values can temporarilydisagree in different ringlets, the cc₋₋ done value in the idle.ccposition might not be the same as the current idle.cc value innon-first-stage switches. When a new idle.ac agreement is reached on theinput ports, that new agreement is broadcast on all output ports(waiting for packets as necessary).

Departure of Packets and Idles from Network

Misrouted packets that depart the network into a ringlet retain theirmarkings in command.mpr as 0 or 1 packets. Correctly routed packets havetheir command.mpr fields set to zero.

Idles departing the network keep the same value as previous departedidles until all of the input idles report an agreed new value ofidle.cc, and retain that agreement for a predetermined length of time(described below), or until a cc₋₋ done idle with opposite value ofidle.cc is received. Then they assume the new value. When the new valueis assumed, idle.ac is also examined--if there is agreement on its valuethe value is transmitted, otherwise the old value is transmitted.Idle.ac never changes unless idle.cc is changing. All exiting idles meetthe SCI specification for a fair-only system.

Calculation of Waiting Time

The time that the final stage switches must wait is that during whichthe agreement might be rescinded due to propagation delays in reportingmisroutes. This waiting period is called cc₋₋ stability₋₋ period and isimplemented with a linear feedback shift register (LFSR) counter in thelast stage switch. In the following, a packet transfer time (PTT) is thetime in clock periods needed for a maximum size packet to pass a pointin the communications system. It is 144 for standard SCI. The maximumpacket length in symbols for some SCI node interface chips is 48, butthere can be two adjacent packets due to deletion of an idle symbol atthe network input port. Switches route this pair as if it were a singlepacket, so that the maximum packet length for routing purposes isactually 96 symbols. The shortest packet transfer time is 4 symbols forthe echo packets.

Worst Case Scenario

The worst case is when a misroute idle and a misrouted packet arrive ata last stage switch at the same time. The misroute idle resets thestability counter and the counter starts counting immediately. The laststage switch does not do anything with the misrouted packet. This ismerely the starting point for counting the time it takes for the packetto traverse a ringlet, generate a misroute idle in the first stage andthe time for the misroute idle to make it to the last stage where itresets the stability counter.

Final Stage to First Stage Ringlet Traversal

The misrouted packet continues onto a ringlet. The longest time it cantake a packet to get through a ringlet happens when all of the nodes onthe ringlet transmit a packet at the same time, filling up all of thebypass FIFO's. The misrouted packet goes through the ringlet, arrivingagain at the network. It takes the packet the following maximum time togo through the ringlet before getting to the first stage:

    longest.sub.-- packet.sub.-- thru.sub.-- ringlet.sub.-- delay=nodes.sub.-- per.sub.-- ringlet* max.sub.-- node.sub.-- delay

where max₋₋ node₋₋ delay is the size of the bypass FIFO in the node.

    longest.sub.-- packet.sub.-- thru.sub.-- ringlet.sub.-- delay=nodes.sub.-- per.sub.-- ringlet* bypass.sub.-- FIFO.sub.-- size

First Stage to Final Stage Broadcast

The first stage switch sees the incoming misroute and broadcasts themisroute idle. The longest that idle can take to get to the last stageis:

    longest.sub.-- idle.sub.-- first.sub.-- to.sub.-- last.sub.-- stage=No of stages*max stage delay

    max stage delay=two back-to-back packet times=PTT

    longest.sub.-- idle.sub.-- first.sub.-- to.sub.-- last.sub.-- stage=S*PTT

Switch pipeline delays are not included in the calculation because forthe worst case a packet is holding up the transmission of the misrouteidle at each switch. The idle proceeds through a parallel pipeline tothe packet and is ready to go as soon as the packet finishes. Theminimum time that it takes a misroute idle to get to the last stage isS*P_(i) where P_(i) is the pipeline delay through a switch for an idle.S*P_(i) is far shorter than S*PTT.

The misroute idle arrives at each last stage switch and all of thestability counters are reset. This occurs at or before the combined timeof the ringlet traversal and the first stage to final stage broadcast

    cc.sub.-- stability.sub.-- period=PTT*S+nodes.sub.-- per.sub.-- ringlet* bypass.sub.-- FIFO.sub.-- size

since the stability counters were last reset. (PTT=packet transfertime=2*packet size, S=number of stages in the network.)

If the stability counters are set to expire at a time longer than thattime, no misrouted packets of that phase can exist when the time iscompleted.

(This analysis does not provide for the occasional deleted or insertedidle, which usually affects the results by a clock period or so, but canaffect them by a packet length in the case where a single idle betweenpackets is deleted. However, the extra packet length is already includedin PTT.)

Detection of Permanent Disagreement

All non-last stage switches use the cc₋₋ stability₋₋ period counter toact as a time-out on the input idle.cc values disagreeing. If thetime-out expires then there is no cc activity in the network and theswitch broadcasts cc₋₋ done(0). There are two parts to calculating howlong a non-last stage switch can see an idle.cc disagreement on itsinputs. The first part has to do with the differential time the laststage cc₋₋ stability₋₋ periods expire. The second part has to do withhow long the change in idle.cc takes to propagate to the next to laststage switch.

Definitions of Variables

Packet transfer time: PTT=max₋₋ length₋₋ packet*2 back₋₋ to₋₋ back₋₋packets=48*2=96 clocks Number of switch stages in the network: S=4 for a16 ringlet system. Number of pipeline stages for idles in the switch:P_(i) =8.5 to 11.0 clocks SCI node interface chip bypass₋₋ FIFO₋₋size=52 FIFO entries=52 clocks

Maximum Differential cc Row to Row Stability Period Expiration

The stability counter in a last stage switch starts to count when theinput idle.cc values all agree. Two different rows will start atdifferent times if idle.cc is delayed on one path and gets through faston the others. Assume that all but row 0 straight path gets through inthe minimum time and row 0 straight path takes the maximum time. Thestraight path on row 0 can not reach all of the last stage switches.Therefore, there is at least one last stage switch that can see idle.ccagreement before row 0. The maximum time it can take a cc change totraverse row 0 straight path and arrive at the last stage switch is:

    (S-1)*PTT

Again, no pipeline delays are included for the worst case because of theparallel paths in the switches for packets and idles. The minimum timefor the fast paths is:

    (S-1)*P.sub.i

Subtracting the two gives the maximum differential time between theslowest and fastest row:

    max.sub.-- row.sub.-- to.sub.-- row.sub.-- stability.sub.-- expiration=(S-1)*PTT-(S-1)*P.sub.i

The differential time of the stability periods expiring could beshortened by cc₋₋ done arriving at the last stage switches. However, theworst case differential time (which is what we want) for cc₋₋ done isalso (S-1)*PTT-(S-1)*P_(i).

Maximum Differential cc Row to Row Propagation

Once the slowest row actually changes idle.cc in the last stage thatchange has to propagate through the node and through the network to thenext-to-last stage switch. We go to the next-to-last stage switchbecause the last stage switch does not check for permanent ccdisagreement. Coming out of the last stage switch the idle. cc changecan be delayed by PTT. The SCI node interface chip bypass FIFO might befull and so the idle.cc change can be delayed by the size of the bypassFIFO. However, the SCI node interface chip delays an idle.cc change byat least one cycle. If there is another packet of size PTT coming inbehind the first packet with the idle.cc change between the two packetsthen idle.cc will be delayed until after the second packet. Tocomplicate things further the SCI node interface chip always tries toput an idle between back to back packets and so PTT would be reduced toPTT/2. If there is something in the bypass FIFO then the delay inidle.cc is done in parallel with the bypass FIFO emptying and so theextra delay would be the bypass FIFO size and not PTT/2. Therefore, ifthe bypass FIFO is empty the delay is PTT/2. If there is something inthe bypass FIFO then the delay is the bypass FIFO size. Up to this pointyou have:

    PTT+max((nodes.sub.-- per.sub.-- ringlet*bypass.sub.-- FIFO.sub.-- size), PTT/2)

    =PTT+(nodes.sub.-- per.sub.-- ringlet*bypass.sub.-- FIFO.sub.-- size)

Once the idle.cc change gets to the first stage switch cc₋₋ done isbroadcast. The counter is reloaded when a switch receives cc₋₋ done,ending the count. (The new value of cc will be following behind cc₋₋done.) The maximum delay caused by the cc₋₋ done broadcast to the nextto last stage switch is (S-2)*PTT. The total time from the last stagethrough the ringlet and then to the next-to-last stage is: ##STR9##Maximum Permanent cc Disagreement Time

The maximum time the next to last stage switch can see idle.ccdisagreement is then: ##STR10## This is approximately twice the size ofthe cc₋₋ stability₋₋ period. The probability of having every stage havea full PTT delay is very low. A more typical case is for the delaythrough each stage to be PTT/2 or just one packet size instead of 2.(This argument also applies to cc₋₋ stability₋₋ period.)

Number of Ringlets Supported

The switch chip has an 11 bit linear feedback shift register counterthat will be used for both the cc stability period and the permanent ccdisagree time-out. This counter can count to 2,047. To find out how manyringlets an 11 bit counter can support solve perm₋₋ cc₋₋ disagree for S(1 node per ringlet):

    S=1+(perm.sub.-- cc.sub.-- disagree-(nodes.sub.-- per.sub.-- ringlet* bypass.sub.-- FIFO.sub.-- size))/(2*PTT-P.sub.i)

    max.sub.-- S=1+(2047-52)/(2*96-8.5)

    max.sub.-- S=11.9

Therefore, we can support a maximum of 11 stages which provides for upto 2,048 ringlets (2 ringlets per row). This is a reasonable number ofringlets for the prototype system. If we use PTT/2 instead of PTT wehave:

    max.sub.-- S=(2047-52)/(2*48-8.5)+1

    max.sub.-- S=23.8

which is more than SCI can handle in the first place.

What is claimed is:
 1. A method of extending the SCI standardinitialization protocol for a switching network which implements thefollowing initialization states:(a) OPERATIONAL, (b) TERMINATE, (c)ABORT, (d) STOP, (e) RESETL, (f) RESETH, (g) FLUSH₋₋ RESETH, comprising:(a) transitioning said switching network from its OPERATIONAL state upondetection at any switch of said network of either an ABORT, a STOP, aRESETL or a RESETH packet on any enabled input port to its TERMINATEstate, (b) terminating the transmission of current packets through saidnetwork while in the TERMINATE state, and (c) transitioning in priorityorder said switching network from the TERMINATE state upon the detectionat any switch of said network on any enabled input port of(i) an ABORTpacket to an ABORT state, or (ii) a STOP packet to a STOP state, or(iii) either a RESETL or a RESETH packet to a RESETL state, and (d) eachtime the switch enters an ABORT state broadcast, a single ABORT followedby a plurality of sync packets to all output ports of said switch, andeach time the switch enters a STOP, a RESETL or a RESETH statebroadcast, a respective STOP, RESETL or RESETH packet to all outputports of said switch along with a plurality of sync packets and thenrepeat until transitioning out of the respective state, and (e) if in anABORT state, transitioning in priority order said network from saidABORT state upon the detection of:(i) a STOP packet on any enabled inputport to said STOP state, or (ii) either a RESETL or a RESETH packet onany enabled input port to said RESETL state, or (f) if in said STOPstate, transitioning said network from said STOP state upon thedetection of(i) either a RESETL or a RESETH packet on any enabled inputport to said RESETL state, or (g) if in said RESETL state, transitioningsaid network from said RESETL state upon detection of a RESETH packet oneach enabled input port to said RESETH state, or (h) if in said RESETHstate, transitioning said network from said RESETH state upon thedetection of idles on each enabled, non-recirculation input port to aFLUSH-RESETH state, and (i) while in said FLUSH-RESETH statebroadcasting idles to all output ports of said switch and transitioningfrom said FLUSH-RESETH state upon detection of idles on all enabledinput ports of said network to said OPERATIONAL state.